this article explores the evolving role of a project manager emphasizing the pmi talent triangle: techni

this article explores the concept of " fake agile " detailing its common symptoms such as extreme

here are some issues i have met while implementing agile. source: freepik some issues i have met whi

every agile transformation looks different but the toughest questions are often the same. from consulting supp

the crystal method is one of the most lightweight and flexible software development methods. it consi

if i could go back in time these are the 18 pieces of advice i would tell my younger s

discover the core of scrum framework: its 3 roles 3 artifacts 5 events 5 values and empirical foundations.scrum is a framework for developing and maintaining complex products. it is an incremental and iterative development process. the entire development process in scrum consists of several short sprint cycles. a short sprint cycle is called a sprint and the recommended sprint length is 2-4 weeks. the product backlog is used to manage stories. the product backlog is a list of stories sorted by business value and the items are mainly user stories. the scrum team always first develops stories of higher value to customers. during the sprint the scrum team selects the stories with top priority from the product backlog for

the crystal method is one of the most lightweight and flexible software development methods. it consi

james greening inventor of agile planning poker. snowbird conference on the eve of the snowbird conferen

the " extreme" in extreme programming refers to applying the principles and practices we agree on to effectively develop software to the limit and practice it frequently such as: " if unit testing is important then we do test-driven development. definition of extreme programming xp the extreme in extreme programming refers to applying the principles and practices we agree on to effectively develop software to the limit and practice it frequently such as: if unit testing is important then we do test-driven development. if integration testing is important so there are multiple integrations in a day and repeated regression testing. pair programming is more of an emphasis on if the code review is good then we keep doing code